Deployment and Federated Composition

Deploy destination

A named address that output deploys to — a folder, or an Amazon S3 bucket with its transport configuration. Short form: destination. Destinations are defined in deploy preferences, in a job's inline deploy settings, or from a file on the AutoMap command line.

Shared destination

One destination that all members of a federation reference by name — the place parcels and shell meet.

Deploy scope

What a deployment publishes and cleans: Everything (the default — the complete site), Groups (content only — for parcel projects), or Shell (site files only — for the shell project).

Parcel

One group's deployed output in a composable Reverb 2.0 site: its content slice plus its deployed record. Parcels are what a composition job assembles.

Chrome

The shell-owned layer of a Reverb site: the entry page, styles, scripts, search page, and root sitemap.

Runtime hash link

A link the Reverb runtime resolves in the reader's browser rather than at generation time: #/<source-id> (landmark), #context/, #page/, and #search/. You author it as an ordinary link — for example, [What's New](#/whats-new) in Markdown++ — and it passes through generation untouched. Since 2026.1, the Links report classifies these links under the Runtime hash link target setting, default Ignore, instead of reporting them as unresolved links.

Deployed record

The small bootstrap files a composable build publishes with its output — wwcomposition.xml and wwcomposition-manifest.html for each group, and wwcomposition-shell.xml for a shell. A composition job reads the deployed records at the destination to learn what is there and where it belongs.

Composable

A format is composable when its deployed output can be assembled into a composed site without rebuilding. Today WebWorks Reverb 2.0 is the composable format.

Member

A job or project a composition references. The shell member supplies the chrome; parcel members supply groups.

Compose

Assemble the deployed output into one site without rebuilding any member. Rerunning it after something changes is recomposing — a table-of-contents-only change recomposes in seconds.

Federated composition

A composition whose members are built and deployed independently by their own teams and jobs, each on its own schedule; the composition only assembles what it finds deployed.

Derivative composition

A composition that builds its members itself and deploys them to its own destination, so one command republishes the whole site. The Build flag on each member is the seam between the two styles, and one composition may mix them member by member.

Merge Settings

The placement declaration: table-of-contents containers wrapping groups. The same grammar appears at three levels — a project target's Merge Settings, a job target's, and a composition's.

Container

A named folder in the composed site's table of contents, declared by Merge Settings. A container is not a group: containers hold groups, and only groups carry content.